Roles and Responsibilities
The table below details the role and the responsibilities associated with creating and using a redundant license:
| Roles | Responsibilities | Tools /Utilities Needed |
|---|---|---|
| Developers | Creating and generating a redundant license | WlscGen or lscgen |
| Customer System Admins (End Users) |
>Setting up a redundant license pool >Adding a redundant license to an existing License Manager pool |
>For defining the redundant License Manager pool you can use any of these options: •WRlfTool (a Windows GUI-based utility) •rlftool (a command line-based utility) •A customized option\utility created using the redundant license configuration file API provided in the lsrlf library. >WlmAdmin (a Windows GUI-based utility) or lsmon (a command line-based utility) for monitoring the redundant License Managers >lspool (a command line-based utility) for temporarily configuring the redundant License Manager information. This utility can also be used for monitoring the redundant License Manager pool. |
Creating Redundant Licenses
If your customers plan to use redundant licenses, you the developer need to provide license codes configured as redundant. You can use WlscGen and lscgen to generate a redundant license code that will be used on redundant License Managers.
To make your license code more secure, you should ask your customer for the following details
>Locking code of Specific computers
If you want to lock the redundant license to specific computers, you must obtain the locking codes of all the redundant License Manager systems. You may also ask your customers for the host names of the computers and record that information with the license code you create (in the log comment or sales order number fields of WlscGen).
>Establishing Majority Rule
Again, to increase security when you create a license code, we strongly recommend you to specify the majority rule. Majority rule dictates that a majority (over half) of the redundant License Managers must be up and running for a request, in order for the request to be serviced. For example, if you have defined five redundant License Managers and majority rule is in effect, at least three of them must be up and running or a request for that license fails. If majority rule is not in effect, your customer may set up the redundant License Managers and can separate them on different networks. Each redundant License Manager, not being able to see any of the others, would then allow your customer to double, triple, quadruple, etc. the total license count without purchasing that many license tokens. The requests for non-redundant licenses or redundant license not using majority rule can continue to be serviced. By default, the majority rule is enabled for supporting three or more redundant License Managers in both WlscGen and lscgen,
Setting up the Redundant License Managers
Refer to the Sentinel RMS SDK System Administrator Guide for the complete steps of setting up the redundant License Manager pool.
Adding a Redundant License to an Existing License Manager Pool
The system administrator can use the lslic utility to add a redundant license code dynamically both in the License Manager memory and/or in the redundant license configuration file. A dynamically added license code is loaded immediately without requiring to restart the redundant License Managers.
For more information on lslic, refer to the Sentinel RMS SDK System Administrator Guide.
Maintaining the Redundant License Manager Pool
The system administrators can maintain the License Managers using the following utilities:
>Use lspool or WlmAdmin to view information about the redundant License Managers and related tasks.
>Use WRlfTool or rlftool or custom utility/option to make changes on the redundant license file.
More information about WlmAdmin, lspool, WRlfTool, and rlftool is included in the Sentinel RMS SDK System Administrator Guide.